-
Notifications
You must be signed in to change notification settings - Fork 82
PR from Jay #512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR from Jay #512
Conversation
🎉 Thank you for your contribution! It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the F5 CLA and reply on a new comment with the following text to agree: I have hereby read the F5 CLA and agree to its terms 2 out of 3 committers have signed the CLA. |
I have hereby read the F5 CLA and agree to its terms. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I'd love to hear your feedback to my comments. Thanks so much for your contribution!
content/nginx/admin-guide/security-controls/securing-http-traffic-upstream.md
Outdated
Show resolved
Hide resolved
content/nginx/admin-guide/security-controls/securing-http-traffic-upstream.md
Outdated
Show resolved
Hide resolved
content/nginx/admin-guide/security-controls/securing-http-traffic-upstream.md
Outdated
Show resolved
Hide resolved
content/nginx/admin-guide/security-controls/securing-http-traffic-upstream.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @jaypolansky1 for your contribution, and congratulations!
All contributors have signed, despite the failing test. |
Proposed changes
Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:
Problem: Give a brief overview of the problem or feature being addressed.
Solution: Explain the approach you took to implement the solution, highlighting any significant design decisions or
considerations.
Testing: Describe any testing that you did.
Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.
If this PR addresses an issue on GitHub, ensure that you link to it here:
Closes #ISSUE
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.md
andCHANGELOG.md
Footnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩